-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PM-12036] Removing ActiveUserState from vault-onboarding.service.ts #12898
base: main
Are you sure you want to change the base?
Conversation
Fixed Issues (14)Great job! The following issues were fixed in this Pull Request
|
Codecov ReportAttention: Patch coverage is
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #12898 +/- ##
==========================================
+ Coverage 35.30% 35.31% +0.01%
==========================================
Files 2996 2996
Lines 90956 90963 +7
Branches 16980 16981 +1
==========================================
+ Hits 32115 32127 +12
+ Misses 56349 56343 -6
- Partials 2492 2493 +1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job, just left some small suggestions.
apps/web/src/app/vault/individual-vault/vault-onboarding/services/vault-onboarding.service.ts
Outdated
Show resolved
Hide resolved
apps/web/src/app/vault/individual-vault/vault-onboarding/vault-onboarding.component.spec.ts
Outdated
Show resolved
Hide resolved
apps/web/src/app/vault/individual-vault/vault-onboarding/vault-onboarding.component.spec.ts
Outdated
Show resolved
Hide resolved
apps/web/src/app/vault/individual-vault/vault-onboarding/vault-onboarding.component.ts
Outdated
Show resolved
Hide resolved
…-onboarding.component.spec.ts Co-authored-by: SmithThe4th <[email protected]>
🎟️ Tracking
📔 Objective
Use SingleUserState not ActiveUserState in vault-onboarding.service
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes